Inductively powered modular medical device system

ABSTRACT

A system includes an inductive backplane, at least one communications interface, and a control unit. The inductive backplane is configured to secure and inductively power a plurality of detachable medical device modules. The control unit controls, via the at least one communications interface, at least one attribute of each medical device module when the medical device module is secured to the inductive backplane. Related apparatus, systems, techniques and articles are also described.

TECHNICAL FIELD

The subject matter described herein relates to a modular medical devicesystem. In particular, the current subject matter is directed to asystem for coordinated operation of multiple medical devices such asinfusion pumps and vital signs monitors.

BACKGROUND

Medical device systems may utilize a plurality of different medicaldevices that are distinct stand-alone or independent medical devices.For example, some conventional infusion pumping systems may include upto about four functionally distinct stand-alone infusion pumps.Conventional infusion pumps are typically stand-alone complex devicesthat are only able to provide independent complex infusion functions. Assuch, coordination or control of the devices collectively is complex anddifficult. Moreover, purchasing of the complex stand-alone devices canbe financially burdensome.

Further, hospitals using each of several different models of pumps, eachemploying distinct user interfaces, makes both learning and practicingtheir operation more time consuming with risk of error elevated. Forinstance, there may be pumps for syringe, large volume, patientcontrolled analgesia, anesthesia and other uses. These difficulties canbe compounded when there are other medical devices being used forpatient care including various types of vital sign monitors and thelike.

SUMMARY

In one aspect, a system includes an inductive backplane, at least onecommunications interface, and a control unit. The inductive backplane isconfigured to secure and inductively power a plurality of detachablemedical device modules. The control unit controls, via the at least onecommunications interface, at least one attribute of each medical devicemodule when the medical device module is secured to the inductivebackplane.

The system can include at least one optical data transceiver and aplurality of first optical data transmission ports along the inductivebackplane, both coupled to the at least one communications interface. Insuch arrangement, the medical device module can include a second opticaldata transmission port positioned along an optical path with acorresponding first optical data transmission port when the medicaldevice module is secured to the inductive backplane. The at least oneoptical data transceiver can be an infrared optical data transmitter. Insome variations, there are a plurality of optical data transceivers andthe at least one communications interface includes a communications buscoupled to each optical data transceiver.

The at least one communications interface can, in other variations, becoupled to the inductive backplane and the control unit can controls,via an induction-based communications protocol, the at least oneattribute of each medical device module when the medical device moduleis secured to the inductive backplane.

The at least one communications interface can wirelessly andcommunicatively couple the control unit to at least one medical devicemodule.

Each medical device module can have an arrangement in which it does notinclude an electrical galvanic connector.

A wide variety of medical device modules can be used with the currentsystem. For example, the system can be used with infusion pumps such assyringe pumps, patient controlled infusion pumps (e.g.,patient-controlled analgesia (PCA) system), large volume infusion pumps,peristaltic pumps, and the like. The medical device modules can also beone or more of a vital signs monitor, cardiac output monitors, gastrictonometers, an SpO2 sensor, an EtCO2 sensor, a blood analyte monitor, anidentification module, a barcode scanner, and a radio frequencyidentification (RFID) scanner.

The inductive backplane can include a plurality of mounting seats, eachmounting seat being configured to mechanically secure one medical devicemodule. The mounting seats can be arranged, for example, along avertical axis of the inductor backplane (e.g., a center line, etc.).Proximity sensors can also be included that correspond to each seat. Theproximity sensors detect presence of a medical device module in thecorresponding seat. The at least one communications interface caninitiate communications with a medical device module in a particularseat after the corresponding proximity sensor detects the presence ofthe medical device module in the seat. In addition or in thealternative, the inductive backplane can commence inductive powering ofa medical device module in a particular seat after the correspondingproximity sensor detects the presence of the medical device module inthe seat. Furthermore, the inductive coupling between the inductivetransmitter and the inductive receiver can be used to characterizeproximity of the medical device module.

The at least one communications interface can be operable to receive andtransmit data from at least one remote computing system via a wiredand/or wireless communication link. The at least one communicationsinterface can be operable to receive and transmit data from at least onemedical device (i.e., a medical device that is not a medical devicemodule) via a wired or wireless connection, the at least one medicaldevice being different from the plurality of medical device modules.

The system can include an auxiliary power source for powering one ormore medical device modules that are not inductively powered. Inaddition, the system can, in some implementations, comprise a batteryfor selectively powering the inductive backplane and the medical devicemodules.

The system can include a touch screen display extending outward from theinductive backplane. An adjustable display arm can couple the touchscreen display with the inductive backplane. The adjustable display armcan be a tilt and swivel arm. In other variations, a touch screendisplay can be integrated into an outer surface of a housing of thesystem. The control unit can control the at least one attribute of oneor more of the medical device modules in response to user-generatedinput received via the touch screen display.

The control unit can controls the at least one attribute of one or moreof the medical device modules in response to data received from a remotesource.

In an interrelated aspect, a system comprises an inductive backplaneconfigured to secure and inductively power a plurality of detachablemedical device modules and a display to display one or more attributesof the medical device modules when secured to the inductive backplane.

In a further interrelated aspect, a medical device module includes atleast one data processor, memory storing instructions for execution bythe at least one data processor, an inductive receiver for powering theat least one data processor, and a housing. The housing has a shape andsize to be secured by an inductive backplane of a modular medical devicesystem. The inductive backplane inductively powering the inductivereceiver when the housing is secured thereto. The modular medical devicesystem can also include at least one communications interface and acontrol unit that controls, via the at least one communicationsinterface, at least one attribute of the medical device module when thehousing is secured to the inductive backplane. In some variations, themedical device module has no external galvanic connection on an outersurface of the housing.

In still a further interrelated aspect, a medical device module caninclude at least one data processor, memory storing instructions forexecution by the at least one data processor, a self-contained powersource, a communications interface, and a housing having a shape andsize to be secured by to a modular medical device system. The medicaldevice module can operate independently when not secured to the modularmedical device system and it can be controlled via the communicationsinterface of the medical device module by the modular medical devicesystem when the medical device module is secured to the modular medicaldevice system.

In another interrelated aspect, an infusion pump includes at least onedata processor, memory storing instructions for execution by the atleast one data processor, and at least one pumping sub-system forpumping fluid passing therethrough (via a tubing set, an IV cassette,etc.). Such an infusion pump can be configured such that it does notinclude an external electrical galvanic connector. In some variations,the infusion pump includes an inductive receiver for being inductivelypowered by an inductive backplane of a modular medical device system.

In a further interrelated aspect, a modular medical device system caninductively power each of a plurality of medical device modules.Thereafter, communications are initiated between each of the medicaldevice modules and a control unit via at least one communicationsinterface. Subsequently, one or more attributes characterizing operationof at least one of the medical device modules are displayed on a displayof the modular medical device system. In some variations, user-generatedinput can be received via the display (or via a different interface)that modifies at least one attribute of at least one medical devicemodule. The control unit of the modular medical device system can themmodify the at least one attribute for the at least one medical devicemodule specified by the user-generated input.

In still another interrelated aspect, a modular medical device systemcan inductively power each of a plurality of medical device modules.Thereafter, communications are initiated between each of the medicaldevice modules and a control unit via at least one communicationsinterface. The control unit then controls one or more attributes of atleast one of the medical device modules.

In some variations, data characterizing the medical device modules whensecured to the inductive backplane can be provided. In this context,provided can include one or more of: displaying the provided data,storing the provided data, loading the provided data into memory, andtransmitting the provided data to at least one remote computing systemor medical device.

Computer program products are also described that comprisenon-transitory computer readable media storing instructions, which whenexecuted one or more data processors of one or more computing systems,causes at least one data processor to perform operations herein.Similarly, computer systems are also described that may include one ormore data processors and a memory coupled to the one or more dataprocessors. The memory may temporarily or permanently store instructionsthat cause at least one processor to perform one or more of theoperations described herein. In addition, methods can be implemented byone or more data processors either within a single computing system ordistributed among two or more computing systems. Such computing systemscan be connected and can exchange data and/or commands or otherinstructions or the like via one or more connections, including but notlimited to a connection over a network (e.g. the Internet, a wirelesswide area network, a local area network, a wide area network, a wirednetwork, or the like), via a direct connection (wired or peer-to-peerwireless) between one or more of the computing systems, etc.

The subject matter described herein provides many advantages. Forexample, the current subject matter provides enhanced usability forclinicians both with regard to the ease of coupling and decouplingmedical device modules from the system and in connection with thevarious user interfaces provided by the system. The current subjectmatter also provides enhanced mobility with regard to the movement ofmedical device modules to be used with other inductive backplanes, withother systems, and stand-alone. Furthermore, the current subject matteris advantageous in that it enables contextual operation of medicaldevice modules thereby increasing safety. Still further, the currentsubject matter is advantageous in that a clinician can scale the numberof utilized medical device modules as may be required during the courseof treatment for a patient. In addition, the current subject matter isadvantageous in that it provides a common unified user interface which,in turn, provides enhanced usability as compared to individualized userinterfaces on each type of medical device.

The details of one or more variations of the subject matter describedherein are set forth in the accompanying drawings and the descriptionbelow. Other features and advantages of the subject matter describedherein will be apparent from the description and drawings, and from theclaims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a modular medical device system;

FIG. 2 is a diagram illustrating a modular medical device system in aclinical setting;

FIG. 3 is a logic diagram illustrating a medical device module;

FIG. 4 is a diagram illustrating a modular medical device system with abackplane extension;

FIG. 5 is a diagram illustrating a compact modular medical devicesystem;

FIG. 6 is a diagram illustrating a modular medical device system withoutan optical communications sub-system;

FIG. 7 is a diagram illustrating a compact modular medical device systemwithout an optical communications sub-system;

FIG. 8 is a diagram illustrating a computing landscape including amodular medical device system;

FIG. 9 is a first process flow diagram illustrating a method ofoperation of a modular medical device system; and

FIG. 10 is a second process flow diagram illustrating a method ofoperation of a modular medical device system.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a diagram 100 illustrating a modular medication device system110. The system 110 comprises a backplane 120 that can be mounted on apole 105. The backplane 120 can mechanically couple to and secure one ormore medical device modules 150 along each of a series of pre-definedmounting seats 112. In some variations, each of the mounting seats 112are uniform in size and spacing, while in other variations differentsizing and/or spacing can be used to accommodate medical device modules150 having different exterior dimensions. In addition, the mountingseats 112 can be arranged along a single axis (e.g., a vertical axis asillustrated, etc.) or they can be arranged along two or more axes. Themounting seats 112 can each have one or more mechanical elements todetachably affix the medical device modules 150 to the backplane 120.

In addition to allowing the medical device modules to be affixed to thesystem, the backplane 120 can provide non-contact inductive power to oneor more medical device modules 150. The backplane 120 can, for eachmounting location, comprise an inductive transmitter 122 for non-contactpowering of a medical device module 150. A corresponding inductivereceiver 152 on the medical device module 150 can, when the medicaldevice module 150 is affixed to the mounting seat 112, be inductivelycoupled with inductive transmitter 122 of backplane 120. In general,energy is sent via an inductive (magnetic) coupling between inductivetransmitter 122 and inductive receiver 152. As a result, there is awireless (no galvanic contact) energy transfer between inductivebackplane 120 and medical device module 150. Moreover, an electricalgalvanic connector, as is typical for powering conventional medicaldevices, is not required to provide power to medical device module 150.Use of non-contacting energy transfer avoids metallic contacts betweenmedical device module 150 and a power source which may be damaged,require special cleaning and pose risk of electrical heating, smoke orfire. Each inductive transmitter 122 can be coupled to an induction bus123 which in turn is connected to a power source 160 (e.g., a wiredconnection to an outlet, a battery, etc.) to enable the inductivecoupling of each inductive transmitter 122.

The backplane 120 can also provide an optical communications interfaceto one or more medical device modules 150 via respective opticalcommunications ports 124 and optical transceivers 126 corresponding toeach mounting seat 112. The medical device modules 150 can havecorresponding optical communications ports 154 and optical transceiver156 which can be optically aligned with the optical communication port124 on the backplane 120 when the medical device module 150 is affixedto the backplane 120 so that a bi-directional data feed can beestablished between the optical transceivers 126, 156. Such data canrelate to a variety of aspects including, but not limited to, datacharacterizing operation of the medical device module 150, data forcontrolling (e.g., modifying, monitoring, etc.) one more attributes ofthe medical device module 150 (e.g., software updates, configurationupdates, asset locations, status information, historical data, patientinformation, patient treatment parameters, medication administrationinformation, etc.), and the like. Stated differently, the data exchangedvia the optical transceivers 126, 156 can comprise any data generated orotherwise used by a medical device module 150 or a caregiver using same.The data transmitted to the backplane 120 can be consumed locally by thesystem 110 and/or it can be transmitted to one or more remotesystems/devices coupled to the system 110 via a wired or wirelesscommunications link. The optical data transceivers 126, 156 can beinfrared (IR) data transceivers such that optical data 146 is propagatedby IR light as the transmission medium. The optical data transceiverscan be coupled to a communications bus 125 that in turn is coupled to acommunications interface 142. The communications interface 142 can, inturn, be coupled to the control unit 140. In addition or in thealternative, a second communications interface 144 can provide anoutward interface for the modular medical device system 110 thatprovides a wired or wireless connection to other devices and/ornetworks. It will be appreciated that any number of communicationsinterfaces can be used, including one communications interface for eachoptical data transceiver 126/seat 112.

The control unit 140 can be hardware, software, or a combination ofboth. For example, the control unit 140 can be a specially designedhardware module including at least one data and memory with specializedsoftware used to control any aspect of a medical device module 150coupled to the system 110. In other cases, the control unit 140 can be asoftware module (or series of modules) used to control any aspect of amedical device module 150 coupled to the system 110. As used herein,unless otherwise specified, the term control shall relate to any type ofdata exchange with a medical device module 150 by the control unit 140including data generated by a medical device module 150 and data used bya medical device module 150 (software updates, power state changes,etc.). For example, the control unit 140 can be used to selectively wakeup medical device modules 150 coupled to the inductive backplane 120from a sleep state. Furthermore, the control unit 140 can be coupled toone or more remote computing systems (via the communications interface144) to allow for the remote control of the medical device modules 150.

Each mounting seat 112 can include a shelf with dove tail featuresextending from a housing of the system 110. Each medical device module150 can include a latch mechanism on a top rear edge that affixes to thehousing of the system 110. The latch mechanism can reduce load on theshelf and can cause the medical device module 150 to rotate back intocontact with the system 110 under load (rather than deflect away fromit). This arrangement can help insure that the inductive transmitter 122is positioned properly and secured in relation to the inductive receiver152.

Each mounting seat 112 can include a proximity sensor 127 that candetect the presence of a medical device module 150. The proximitysensors 127 can be optical, electric, electro-mechanical, and/ormechanical devices. For example, the proximity sensors 127 can comprisea Hall effect sensor and/or a mechanical switch. The presence of amedical device module 150 can be used to initiate, for example,inductive powering by the corresponding inductive transmitter 122 and/orcommunications via the communications interface 142. The proximitysensor 127 can also indicate an alarm condition when a medical devicemodule 150 is not completely secured so that appropriate actions can betaken.

Medical device module 150 can be any medical device that is compatiblefor scalability in a modular medical device system. For instance, themodular medical device system 110 can utilize one or more medical devicemodules 150 depending on the functionality that is needed for propercare of a patient. Moreover, a modular medical device system 110 can bescaled up to incorporate additional medical device modules 150 and alsoscaled down by removing medical device modules 150.

For example, if patient care requires only one infusion pump, then themodular medical device system 110 can include a single affixed infusionpump. Moreover, if patient care requires two infusion pumps, then themodular medical device system 110 can be scaled up to include an affixedadditional infusion pump.

Medical device modules 150 can include, but is not limited to, aninfusion pump (e.g., a large volume pump (LVP), a syringe pump), apatient-controlled analgesia (PCA) system, a vital signs monitor (VSM)(e.g., an SpO2 sensor, an EtCO2 sensors, cardiac output monitors,gastric tonometers, etc.), a bedside blood analyte analyzer (e.g. bloodglucose), an Auto-ID module (barcode scanner and RFID), and otherdevices which measure physiological parameters associated with a patientand/or assist with the clinical care of the patient (and such medicaldevice modules 150 may not necessarily measure physiological parametersof the patient).

Modular medical device system 110 can also comprise a display unit 130that provides a unified interface that characterizes the operation ofvarious medical device modules 150 coupled to the backplane 120. Thedisplay unit 130 can comprise a touch screen interface that allows auser to selectively view and alter performance parameters/metrics ofindividual medical device modules 150, concurrently view performanceparameters/metrics of multiple medical device modules 150, andadditionally orchestrate complex sequences of infusions/operations frommultiple medical device modules 150. The display unit 130 can be affixedto an outer housing of the modular medical device system 130/inductivebackplane 120 by a tilt and swivel arm mount that allows the displayunit to be moved on different sides of the system 110 and/or to changevarying positions (to accommodate different positions/heights ofcaregivers).

The display unit 130 can include a speaker to provide audio cuesrelating to various aspects of medical device modules 150 (in otherversions the speaker is located elsewhere in the system 110). When themedical device modules 150 are coupled to the backplane 120, audio cuessuch as alarms for such medical device modules 150 can be delegated sothat the system 110 handles the alarms whether via an audio and/orvisual cue in the display unit 130 or by an audio cue generatedelsewhere in the system 110. In some cases, some alarms can be still behandled by a medical device module 150 while other alarms are handled bythe system 110.

FIG. 2 is a diagram 200 illustrating a modular medical device system 110in a clinical setting. In particular, in this view, the modular medicaldevice system 110 is coupled to two infusion pumps 150A, 150B, a vitalsigns monitor 150C, and a syringe pump 150D. The infusion pumps 150A and150B are respectively fluidically coupled to two fluid/medicationcontainers 222, 224 suspended from an IV pole 220. In addition, each ofthe infusion pumps 150A and 150B and the syringe pump 150D arefluidically coupled to an IV catheter inserted into a patient 210 sothat the corresponding fluids can be delivered to the patient. Themodular medical device system 110 monitors and/or controls how fluidsfrom the respective sources 150A, 150B, 150D are delivered to thepatient 210. It will be appreciated that varying numbers of medicaldevice modules 150 can be utilized depending on the particular conditionof and/or treatment the patient 210.

FIG. 3 is a logic diagram 300 of a medical device module 150. With FIG.3, each medical device module 150 can include a secondary power source156 such as a battery or a wired connection to an external power source.For example, the secondary power source 156 can power medical devicemodule 120 when inductive receiver 152 is unable to power medical devicemodule 150. In one scenario, medical device module 150 is an infusionpump that is associated with (and fluidly communicating with) a patient.If the patient is moved to another location (e.g., to an x-ray roomwhich is away from inductive backplane 110), then medical device module150 must also move with the patient away from inductive backplane 120 inorder to continue the current infusion without interruption. Upon acertain distance from inductive backplane 120, inductive receiver 152cannot be energized by inductive backplane 120 and therefore cannotpower medical device module 150. In other cases, the inductive backplane120 may be turned off or operating in a mode not allowing the inductivereceiver 152 to be energized. Accordingly, power source 156 (which mayalso be charged through inductive receiver 152) is able to provide therequisite power for medical device module 150. In one variation, thepower source 156 is a battery that can keep medical device module 150operational in a range of about two to four hours.

Each medical device module 150 can also include memory 157 and at leastone data processor 158. The memory 157 can store instructions forexecution by the at least one data processor 158 for use, for example,in the operation of the medical device module in a clinical setting. Thememory 157 can also store data relating to the operation of the medicaldevice module such as data characterizing how the medical device module150 is used and parameters relating to same (e.g., number of hoursoperated, thresholds for alerts, etc.), performance and statusinformation, and well as other aspects relating to the use of suchmedical device module 150 such as patient data, medicationadministration data, patient treatment parameters, etc. It is noted thatwhen a medical device module 150 is reattached to the prior inductivebackplane or a different inductive backplane, information required tocontinue the infusion stored in memory 157, without interruption, can betransmitted from the medical device module 150 to the backplane (and tothe control unit 140).

Each medical device module 150 can also comprise an additionalcommunications interface 159 other than the optical data transceiver 154(in some variations the optical data transceiver 154 may not form partof the medical device module 150 and so the communications interface 159may be the only gateway for communication outside of the medical devicemodule 150). This communications interface 159 can be fixed and/orwireless and be used to communicate to computer networks andpeer-to-peer pairing with other devices when the medical device module150 is not coupled to the backplane 120.

In some implementations, the communications interface 159 can be used inaddition or instead of the optical data transceiver 154 when the medicaldevice module 150 is coupled to the backplane 120. For example, themedical device module 150 can be seated on the backplane 120 but nothave an optical data transceiver. In such a scenario, the communicationsinterface 159 can wirelessly communicate with the control unit 140 ofthe modular medical device system 110 so that the operation of themedical device module 150 can be monitored and/or controlled by themodular medical device system 110 (whether or not the medical devicemodule 150 is seated). Various types of wireless communications can beused (for this and other aspects described herein) such as shortdistance protocols such as BLUETOOTH, near field communication (NFC),WiFi, ZIGBEE, and the like.

As noted above, the system 110 comprises a control unit 140 (which inturn can comprise at least one data processor and memory for storinginstructions for execution by the at least one data processor and/ordata characterizing or otherwise relating to the operation of medicationdevice modules 150). The control unit 140 can act to individuallymonitor and/or control the operation of the medical device modules 150affixed to the backplane 120 such that the functionality of the medicaldevice modules 150, alone and/or in combination are increased. In somecases, the control unit 140 can orchestrate the operation of multiplemedical device modules 150. For example, certain sequences of operationand/or concurrent operation can be defined amongst the medical devicemodules 150. Such an arrangement can permit, for example, coordinatedinfusion from different fluid sources. Some medical device modules 150can have the ability to function fully independent of the control unit140 for the purpose of basic operations. However, the modules acquiremore complex abilities and functionality when operating under thecommand and coordination of the controller.

FIG. 4 is a diagram 400 that illustrates a backplane extension 410. Thebackplane extension 410 provides additional seats 112 to which medicaldevice modules 150 can be coupled. The backplane extension 410 can becoupled physically and/or electrically to the system 110 so that anymedical device modules 150 coupled to the backplane extension 410 can becoupled to the control unit 140 and function in a similar manner to themedical device modules 150 coupled to the backplane 120. Stateddifferently, backplane extension 410 can function similarly to theinductive backplane 120. It will be appreciated that the backplane 120and the backplane extension 410 can each be configured to seat anynumber of medical device modules 150 as may be desired.

In some clinical settings, multiple backplane extensions 410 and/orbackplanes 120 can be utilized to serve a single patient. With such anarrangement, each inductive backplane 120 and backplane extension 410can have local communication with the other inductive backplanes 120,410 serving the same patient to provide coordination of functionalityand data. The communication can be wired and/or wireless using, forexample, short range digital radio technology, WiFi, optical datatransceivers, BLUETOOTH, ZIGBEE, NFC, and the like.

FIG. 5 is a diagram 500 that illustrates a variation of a modularmedical device system 510 that is more compact. This modular medicaldevice system 120 can, for example, include fewer seats 112 to whichmedical device modules 150 can be affixed, than the modular medicaldevice system 110 (illustrated in FIG. 1) to allow it to sit on a tabletop or other flat surface. In addition, the display 520 can be placedimmediately above the medical device modules 150 to further decrease thefootprint of the modular medical device system 520.

FIG. 6 is a diagram 600 of a modular medical device system 610 and FIG.7 is a diagram 700 of a compact modular medical device system 710 thatrespectively illustrate alternative implementations to the modularmedical device system 110 of FIG. 1 and the compact modular medicaldevice system 510 of FIG. 5. With both of these variations,communications with medical device modules 150 are effected using acommunications protocol different from the optical sub-systems (124,125, 126, 142). For example, in some variations, the inductivetransmitters 122 and inductive bus 123 can be used to exchange data withthe inductive receiver 152 to effect a near field magnetic inductioncommunication system. Such an arrangement can provide a short rangewireless physical layer that communicates by coupling a tight,low-power, non-propagating magnetic field between the inductivetransmitter 122 and the inductive receiver 152. The transmitter coil inthe inductive transmitter 122 can modulate a magnetic field which ismeasured by the inductive receiver 152 in another device. It will beappreciated that the communications are bi-directional and as such, theinductive receiver 152 can also transmit data to the inductivetransmitter 122.

In other variations, the modular medical device systems 610, 710 cancommunicate and exchange data with the medical device modules 150 via awireless communications protocol including, but not limited to shortrange digital radio technology, WiFi, optical data transceivers,BLUETOOTH, ZIGBEE, NFC, and the like.

FIG. 8 is a system diagram illustrating a computing landscape 800 withina healthcare environment such as a hospital that includes modularmedical device systems 110, 510. Various devices and systems, both localto the healthcare environment and remote from the healthcareenvironment, can interact via at least one computing network 805. Thiscomputing network 805 can provide any form or medium of digitalcommunication connectivity (i.e., wired or wireless) amongst the variousdevices and systems. Examples of communication networks include a localarea network (“LAN”), a wide area network (“WAN”), and the Internet. Insome cases, one or more of the various devices and systems can interactdirectly via peer-to-peer coupling (either via a hardwired connection orvia a wireless protocol such as Bluetooth or WiFi). In addition, in somevariations, one or more of the devices and systems communicate via acellular data network.

The modular medical device systems 110, 150 can include at least onecommunications interface that can access the computing network 805either via a fixed wired connection or via a wireless connection (via,for example, one or more access points). In addition, the modularmedical device systems 110, 150 can also couple to other componentswithin the computing landscape 800 via direct wired or wirelesspeer-to-peer coupling (not shown). Furthermore, in some cases, one ormore of the modular medical device systems 110, 510 can beself-contained and is not connected to any other devices or networks.The modular medical device systems 110, 510 can transmit data via thecomputing network 805 to any of the other components within thelandscape 800 that characterizes the medical device modules 150. Inaddition, the modular medical device systems 110, 510 can receive datafrom the computing network 805 relating to monitoring and in some casescontrolling one or more attributes of the medical device modules 150(e.g., software updates, configuration updates, historical data, statusinformation, assets location, patient information, etc.).

In particular, aspects of the computing landscape 800 can be implementedin a computing system that includes a back-end component (e.g., as adata server 810), or that includes a middleware component (e.g., anapplication server 815), or that includes a front-end component (e.g., aclient computer 820 having a graphical user interface or a Web browserthrough which a user may interact with an implementation of the subjectmatter described herein), or any combination of such back-end,middleware, or front-end components. A client 820 and server 810, 815are generally remote from each other and typically interact through thecommunications network 805. The relationship of the clients 820 andservers 810, 815 arises by virtue of computer programs running on therespective computers and having a client-server relationship to eachother. Clients 820 can be any of a variety of computing platforms thatinclude local applications for providing various functionality withinthe healthcare environment. Example clients 820 include, but are notlimited to, desktop computers, laptop computers, tablets, and othercomputers with touch-screen interfaces. The local applications can beself-contained in that they do not require network connectivity and/orthey can interact with one or more of the servers 810, 815 (e.g., a webbrowser).

A variety of applications can be executed on the various devices andsystems within the computing landscape such as electronic health recordapplications, medical device monitoring, operation, and maintenanceapplications, scheduling applications, billing applications and thelike. As another example, the applications can comprise a collection ofenterprise-based applications that provide dose error reduction software(DERS) for the modular medical device systems 110, 150 incorporates arole-based view of infusion data, provides a comprehensive platform forconnectivity to external hospital applications, and enables directedmaintenance and calibration activities for devices, storage of clinicaland device history, etc. As a further example, the applications canprovide for remote alarms management and/or asset tracking for medicaldevice modules 150 coupled to one or more of the modular medical devicesystems 110, 150.

The network 805 can be coupled to one or more data storage systems 825.The data storage systems 825 can include databases providing physicaldata storage within the healthcare environment or within a dedicatedfacility. In addition, or in the alternative, the data storage systems825 can include cloud-based systems providing remote storage of data in,for example, a multi-tenant computing environment. The data storagesystems 825 can also comprise non-transitory computer readable media.

Mobile communications devices (MCDs) 830 can also form part of thecomputing landscape 800. The MCDs 830 can communicate directly via thenetwork 805 and/or they can communicate with the network 805 via anintermediate network such as a cellular data network. Various types ofcommunication protocols can be used by the MCDs 830 including, forexample, messaging protocols such as SMS and MMS. In some cases, theMCDs 830 can receive alerts generated from the operation of the medicaldevice modules 150 coupled to the backplane 120 and/or they canotherwise be used to monitor the operation of such medical devicemodules 150.

Various types of medical devices 840 can be used as part of thecomputing landscape 800. These medical devices 840 can comprise, unlessotherwise specified, any type of device or system with a communicationsinterface that characterizes one or more physiological measurements of apatient and/or that characterize or are used for the treatment of apatient. In some cases, the medical devices 840 communicate via peer topeer wired or wireless communications with another medical device 840(as opposed to communicating with the network 805). For example, themedical device 840 can comprise a bedside vital signs monitor that isconnected to other medical devices 840 (and/or the modular medicaldevice system 110, 510), namely a wireless pulse oximeter and to a wiredblood pressure monitor. One or more attributes of the medical devices840 can be locally controlled by a clinician, controlled via a clinicianvia the network 805, and/or they can be controlled by one or more of aserver 810, 815, a client 620, a MCD 830, and/or another medical device840 or the modular medical device systems 110, 510.

The computing landscape 800 can provide various types of functionalityas may be required within a healthcare environment such as a hospital.For example, a pharmacy can initiate a prescription via one of theclient computers 820. This prescription can be stored in the datastorage 825 and/or pushed out to other clients 820, an MCD 830, and/orone or more of the medical devices 840 and/or one of the medical devicemodules 150 forming part of the modular medical device system 110. Inaddition, the medical devices 840 and the modular medical device system110 can provide data characterizing one or more physiologicalmeasurements of a patient and/or treatment of a patient (e.g., medicaldevice 840 can be an infusion management system, etc.). The datagenerated by the modular medical device system 110 and the medicaldevices 840 can be communicated to other medical devices 840, theservers 810, 815, the clients 820, the MCDs 830, and/or stored in thedata storage systems 825.

Various methods can be implemented in accordance with the currentsubject matter. FIG. 9 is a process flow diagram 900 illustrating amethod in which, at 910, a modular medical device system inductivelypowers each of a plurality of medical device modules. The modularmedical device system includes an inductive backplane configured tosecure and inductively power the plurality of medical device modules, acommunications interface, a display, and a control unit. The controlunit can control at least one attribute of each medical device modulevia the communications interface when the medical device module issecured to the inductive backplane. Thereafter, at 920, communicationsare initiated between each of the medical device modules and the controlunit via the communications interface. The display, at 930, thendisplays one or more attributes characterizing operation of at least oneof the medical device modules. In addition, optionally, at 940,user-generated input modifying at least one attribute of at least onemedical device module is receiving via the display of the modularmedical device system. As a result, at 950, the control unit modifiesthe at least one attribute for the at least one medical device module asspecified by the user-generated input. In other scenarios, one or moreattributes of the medical device modules can be modified from acomponent/source remote from the modular medical device system.

FIG. 10 is a process flow diagram 1000 illustrating a method in which,at 1010, a modular medical device system inductively powers each of aplurality of medical device modules. The modular medical device systemincludes an inductive backplane configured to secure and inductivelypower the plurality of medical device modules, a communicationsinterface, a display, and a control unit. The control unit can controlat least one attribute of each medical device module via thecommunications interface when the medical device module is secured tothe inductive backplane. Thereafter, at 1020, communications isinitiated between each of the medical device modules and the controlunit via the at least one communications interface. One or moreattributes of at least one of the medical device modules are then, at1030, controlled by the control unit.

The following U.S. patent applications each filed on Mar. 14, 2013describe infusion pumps and infusion pump mechanisms that can be used inconnection with the current subject matter and are all herebyincorporated by reference in their entirety: U.S. patent applicationSer. No. 13/827,775 entitled “Pump Segment Placement”; U.S. patentapplication Ser. No. 13/827,036 entitled “Memory and IdentificationAssociated With IV Set”; U.S. patent application Ser. No. 13/828,777entitled “Cooperation of Platen and Pump Cassette for Pump Device”; U.S.patent application Ser. No. 13/829,425 entitled “Rotary Valve for aDisposable Infusion Set”; U.S. patent application Ser. No. 13/829,854entitled “Infusion Pump Configured to Engage a Sensor With Tubing”; andU.S. patent application Ser. No. 13/830,175 entitled “IV System toAssist With Line Management”.

One or more aspects or features of the subject matter described hereinmay be realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device (e.g., mouse, touch screen, etc.), andat least one output device.

These computer programs, which can also be referred to programs,software, software applications, applications, components, or code,include machine instructions for a programmable processor, and can beimplemented in a high-level procedural language, an object-orientedprogramming language, a functional programming language, a logicalprogramming language, and/or in assembly/machine language. As usedherein, the term “machine-readable medium” refers to any computerprogram product, apparatus and/or device, such as for example magneticdiscs, optical disks, memory, and Programmable Logic Devices (PLDs),used to provide machine instructions and/or data to a programmableprocessor, including a machine-readable medium that receives machineinstructions as a machine-readable signal. The term “machine-readablesignal” refers to any signal used to provide machine instructions and/ordata to a programmable processor. The machine-readable medium can storesuch machine instructions non-transitorily, such as for example as woulda non-transient solid state memory or a magnetic hard drive or anyequivalent storage medium. The machine-readable medium can alternativelyor additionally store such machine instructions in a transient manner,such as for example as would a processor cache or other random accessmemory associated with one or more physical processor cores.

With certain aspects, to provide for interaction with a user, thesubject matter described herein can be implemented on a computer havinga display device, such as for example a cathode ray tube (CRT) or aliquid crystal display (LCD) monitor for displaying information to theuser and a keyboard and a pointing device, such as for example a mouseor a trackball, by which the user may provide input to the computer.Other kinds of devices can be used to provide for interaction with auser as well. For example, feedback provided to the user can be any formof sensory feedback, such as for example visual feedback, auditoryfeedback, or tactile feedback; and input from the user may be receivedin any form, including, but not limited to, acoustic, speech, or tactileinput. Other possible input devices include, but are not limited to,touch screens or other touch-sensitive devices such as single ormulti-point resistive or capacitive trackpads, voice recognitionhardware and software, optical scanners, optical pointers, digital imagecapture devices and associated interpretation software, and the like.

The subject matter described herein may be implemented in a computingsystem that includes a back-end component (e.g., as a data server), orthat includes a middleware component (e.g., an application server), orthat includes a front-end component (e.g., a client computer having agraphical user interface or a Web browser through which a user mayinteract with an implementation of the subject matter described herein),or any combination of such back-end, middleware, or front-endcomponents. The components of the system may be interconnected by anyform or medium of digital data communication (e.g., a communicationnetwork). Examples of communication networks include a local areanetwork (“LAN”), a wide area network (“WAN”), the Internet, WiFI (IEEE802.11 standards), NFC, BLUETOOTH, ZIGBEE, and the like.

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

The subject matter described herein can be embodied in systems,apparatus, methods, and/or articles depending on the desiredconfiguration. The implementations set forth in the foregoingdescription do not represent all implementations consistent with thesubject matter described herein. Instead, they are merely some examplesconsistent with aspects related to the described subject matter.Although a few variations have been described in detail above, othermodifications or additions are possible. In particular, further featuresand/or variations can be provided in addition to those set forth herein.For example, the implementations described above can be directed tovarious combinations and subcombinations of the disclosed featuresand/or combinations and subcombinations of several further featuresdisclosed above. In addition, the logic flow(s) depicted in theaccompanying figures and/or described herein do not necessarily requirethe particular order shown, or sequential order, to achieve desirableresults. Other implementations may be within the scope of the followingclaims.

What is claimed is:
 1. A system comprising: an inductive backplaneconfigured to secure and inductively power a plurality of detachablemedical device modules, the inductive backplane including a plurality ofmounting seats, each mounting seat being configured to mechanicallysecure to a medical device module; a dedicated inductive transmitterpositioned at each of the mounting seats of the inductive backplane,each dedicated inductive transmitter adapted to couple to acorresponding inductive receiver of a corresponding medical devicemodule when the corresponding medical device module is positioned on themounting seat such that the inductive backplane provides non-contact,inductive power to the corresponding medical device module via acoupling between the inductive transmitter and the correspondinginductive receiver of the corresponding medical device module; at leastone communications interface located at each of the mounting seats; anda control unit to control, via the at least one communicationsinterface, an infusion attribute of each medical device module when themedical device module is secured to the inductive backplane.
 2. A systemas in claim 1, further comprising: at least one optical data transceivercoupled to the at least one communications interface; and a plurality offirst optical data transmission ports along the inductive backplanecoupled to the at least one communications interface; wherein eachmedical device module comprises a second optical data transmission portpositioned along an optical path with a corresponding first optical datatransmission port when the medical device module is secured to theinductive backplane.
 3. A system as in claim 2, wherein the at least oneoptical data transceiver is an infrared optical data transmitter.
 4. Asystem as in claim 1, wherein there are a plurality of optical datatransceivers and the at least one communications interface comprises acommunications bus coupled to each optical data transceiver.
 5. A systemas in claim 1, wherein there are a plurality of optical datatransceivers and a plurality of communications interfaces that eachcorrespond to a different optical data transceiver.
 6. A system as inclaim 1, wherein the at least one communications interface is coupled tothe inductive backplane and the control unit controls, via aninduction-based communications protocol, the infusion attribute of eachmedical device module when the medical device module is secured to theinductive backplane.
 7. A system as in claim 1, wherein the at least onecommunications interface wirelessly couples the control unit to at leastone medical device module.
 8. A system as in claim 1, wherein eachmedical device module does not comprise an electrical galvanicconnector.
 9. A system as in claim 1, wherein the plurality of medicaldevice modules comprise at least one fluid infusion pump.
 10. A systemas in claim 9, wherein the at least one fluid infusion pump is selectedfrom a group consisting of: syringe pumps, patient controlled infusionpumps, large volume infusion pumps, and peristaltic pumps.
 11. A systemas in claim 1, wherein the plurality of medical device modules comprisea patient-controlled analgesia (PCA) system.
 12. A system as in claim 1,wherein the plurality of medical device modules comprises at least oneof: a vital signs monitor, a blood analyte monitor, cardiac outputmonitors, gastric tonometers, an SpO2 sensor, an EtCO2 sensor, anidentification module, a barcode scanner, and a radio frequencyidentification (RFID) scanner.
 13. A system as in claim 1, wherein theplurality of mounting seats are arranged along a vertical axis of theinductor backplane.
 14. A system as in claim 1, further comprising aproximity sensor corresponding to each seat, the proximity sensordetecting presence of a medical device module in the corresponding seat.15. A system as in claim 14, wherein the at least one communicationsinterface initiates communications with a medical device module in aparticular seat after the corresponding proximity sensor detects thepresence of the medical device module in the seat.
 16. A system as inclaim 14, wherein the inductive backplane commences inductive poweringof a medical device module in a particular seat after the correspondingproximity sensor detects the presence of the medical device module inthe seat.
 17. A system as in claim 1, wherein the at least onecommunications interface operable to receive and transmit data from atleast one remote computing system.
 18. A system as in claim 1, whereinthe at least one communications interface is operable to receive andtransmit data from at least one medical device via a wired or wirelessconnection, the at least one medical device being different from theplurality of medical device modules.
 19. A system as in claim 1, furthercomprising: an auxiliary power source for powering one or more medicaldevice modules that are not inductively powered.
 20. A system as inclaim 1, further comprising: a battery for selectively powering theinductive backplane and the medical device modules.
 21. A system as inclaim 1, further comprising: a touch screen display.
 22. A system as inclaim 21, further comprising: an adjustable display arm coupling thetouch screen display with the inductive backplane.
 23. A system as inclaim 22, wherein the adjustable display arm is a tilt and swivel arm.24. A system as in claim 21, further comprising: a housing envelopingthe inductive backplane; wherein the touch screen display is integratedinto an outer surface of the housing.
 25. A system as in claim 21,wherein the control unit controls the infusion attribute of one or moreof the medical device modules in response to user-generated inputreceived via the touch screen display.
 26. A system as in claim 1,wherein the control unit controls the infusion attribute of one or moreof the medical device modules in response to data received from a remotesource.